-
Notifications
You must be signed in to change notification settings - Fork 39
fix(deps): update react j:kit-282 #6192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request ReportPR Title✅ Title follows the conventional commit spec. Live demo linksBundle Size
|
dd3e1d6 to
6e27fb9
Compare
6e27fb9 to
21d5727
Compare
21d5727 to
a23ebb8
Compare
a23ebb8 to
3f1f7e1
Compare
3f1f7e1 to
d2fe5b7
Compare
louis-bompart
approved these changes
Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.3.13->3.3.191.0.6->1.0.87.8.2->7.9.47.8.2->7.9.47.8.2->7.9.47.8.2->7.9.419.2.0->19.2.219.2.0->19.2.25.0.3->5.0.415.2.4->15.5.67.8.2->7.9.4Release Notes
coveo/ui-kit (@coveo/atomic-react)
v3.3.19Compare Source
v3.3.18Compare Source
v3.3.17Compare Source
v3.3.16Compare Source
v3.3.15Compare Source
v3.3.14Compare Source
lit/lit (@lit/react)
v1.0.8Compare Source
Patch Changes
aea85e24- Update READMEv1.0.7Compare Source
Patch Changes
dd2fdc96Thanks @Artur-! - fix: Widen range for React types to include React 19remix-run/react-router (@react-router/dev)
v7.9.4Compare Source
Patch Changes
Update
valibotdependency to^1.1.0(#14379)New (unstable)
useRoutehook for accessing data from specific routes (#14407)For example, let's say you have an
adminroute somewhere in your app and you want any child routes ofadminto all have access to theloaderDataandactionDatafromadmin.You might even want to create a reusable widget that all of the routes nested under
admincould use:In framework mode,
useRouteknows all your app's routes and gives you TS errors when invalid route IDs are passed in:useRoutereturnsundefinedif the route is not part of the current page:Note: the
rootroute is the exception since it is guaranteed to be part of the current page.As a result,
useRoutenever returnsundefinedforroot.loaderDataandactionDataare marked as optional since they could be accessed before theactionis triggered or after theloaderthrew an error:If instead of a specific route, you wanted access to the current route's
loaderDataandactionData, you can calluseRoutewithout arguments:This usage is equivalent to calling
useLoaderDataanduseActionData, but consolidates all route data access into one hook:useRoute.Note: when calling
useRoute()(without a route ID), TS has no way to know which route is the current route.As a result,
loaderDataandactionDataare typed asunknown.If you want more type-safety, you can either narrow the type yourself with something like
zodor you can refactor your app to pass down typed props to yourAdminWidget:Updated dependencies:
[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.3Compare Source
Patch Changes
[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.2Compare Source
Patch Changes
Fix preset future flags being ignored during config resolution (#14369)
Fixes a bug where future flags defined by presets were completely ignored. The config resolution was incorrectly reading from
reactRouterUserConfig.futureinstead of the mergeduserAndPresetConfigs.future, causing all preset-defined future flags to be lost.This fix ensures presets can properly enable experimental features as intended by the preset system design.
Add unstable support for RSC Framework Mode (#14336)
Switch internal vite plugin Response logic to use
@remix-run/node-fetch-server(#13927)Updated dependencies:
[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.1Compare Source
Patch Changes
Futureinterface naming frommiddleware->v8_middleware(#14327)[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.0Compare Source
Minor Changes
Stabilize middleware and context APIs. (#14215)
We have removed the
unstable_prefix from the following APIs and they are now considered stable and ready for production use:RouterContextProvidercreateContextcreateBrowserRoutergetContextoption<HydratedRouter>getContextpropPlease see the Middleware Docs, the Middleware RFC, and the Client-side Context RFC for more information.
Patch Changes
[email protected]@react-router/[email protected]@react-router/[email protected]remix-run/react-router (@react-router/fs-routes)
v7.9.4Compare Source
Patch Changes
@react-router/[email protected]v7.9.3Compare Source
Patch Changes
@react-router/[email protected]v7.9.2Compare Source
Patch Changes
@react-router/[email protected]v7.9.1Compare Source
Patch Changes
@react-router/[email protected]v7.9.0Compare Source
Patch Changes
@react-router/[email protected]remix-run/react-router (@react-router/node)
v7.9.4Compare Source
Patch Changes
[email protected]v7.9.3Compare Source
Patch Changes
[email protected]v7.9.2Compare Source
Patch Changes
[email protected]v7.9.1Compare Source
Patch Changes
[email protected]v7.9.0Compare Source
Minor Changes
Stabilize middleware and context APIs. (#14215)
We have removed the
unstable_prefix from the following APIs and they are now considered stable and ready for production use:RouterContextProvidercreateContextcreateBrowserRoutergetContextoption<HydratedRouter>getContextpropPlease see the Middleware Docs, the Middleware RFC, and the Client-side Context RFC for more information.
Patch Changes
[email protected]remix-run/react-router (@react-router/serve)
v7.9.4Compare Source
Patch Changes
[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.3Compare Source
Patch Changes
[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.2Compare Source
Patch Changes
[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.1Compare Source
Patch Changes
[email protected]@react-router/[email protected]@react-router/[email protected]v7.9.0Compare Source
Patch Changes
[email protected]@react-router/[email protected]@react-router/[email protected]vitejs/vite-plugin-react (@vitejs/plugin-react)
v5.0.4Compare Source
Perf: use native refresh wrapper plugin in rolldown-vite (#881)
vercel/next.js (next)
v15.5.6Compare Source
Core Changes
Credits
Huge thanks to @mischnic for helping!
v15.5.5Compare Source
Core Changes
experimental.middlewareClientMaxBodySizebody cloning limit (#84722)Misc Changes
Credits
Huge thanks to @devjiwonchoi, @ztanner, and @icyJoseph for helping!
v15.5.4Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @yiminghe, @huozhi, @devjiwonchoi, @mischnic, @lukesandberg, @ztanner, @icyJoseph, @leerob, @fufuShih, @dwrth, @aymericzip, @obendev, @molebox, @OoMNoO, @pontasan, @styfle, @HondaYt, @ryuapp, @lpalmes, and @ijjk for helping!
v15.5.3Compare Source
Core Changes
Credits
Huge thanks to @bgub for helping!
v15.5.2Compare Source
Core Changes
Credits
Huge thanks to @bgub and @ztanner for helping!
v15.5.1Compare Source
Core Changes
Credits
Huge thanks to @bgub, @mischnic, and @ztanner for helping!
v15.5.0Compare Source
Core Changes
@typescript-eslint/switch-exhaustiveness-checkrule: #81583React.unstable_postpone(): #81652images.qualitiesis undefined: #81690pprordynamicIOenabled: #81668__turbopack_load_by_url__: #8166397cdd5d3-20250710to2f0e7e57-20250715: #81678renderToStringfunction: #817072f0e7e57-20250715tod85ec5f5-20250716: #81708next-serverVM: #81664headers/cookies/draftModein'use cache': #81716d85ec5f5-20250716todffacc7b-20250717: #81767getExpectedRequestStorefunction: #81791.next/cache: #81807dffacc7b-20250717toe9638c33-20250721: #81899'use cache: private': #81816browserslist: #81851run-turbopack-compilertrace span: #81917e9638c33-20250721to7513996f-20250722: #819407513996f-20250722toedac0dde-20250723: #81984exhaustive-depsviolations: #82010edac0dde-20250723to3d14fcf0-20250724: #820203d14fcf0-20250724to19baee81-20250725: #8206319baee81-20250725toeaee5308-20250728: #82120eaee5308-20250728to9be531cd-20250729: #82159@next/codemod: update docs url in README: #82135@next/codemod: Addexperimental.turbototurbopackcodemod for Next.js configs: #82134NextRequesttypes: #821729be531cd-20250729to9784cb37-20250730: #82207TURBOPACKenv before loading config: #82162outputFileTracingRootorturbopack.rootoption is provided: #821649784cb37-20250730toc260b38d-20250731: #82247eslint-plugin-react-hooksin React sync: #82294Configuration
📅 Schedule: Branch creation - "before 4:00am on Tuesday" in timezone America/Toronto, Automerge - "after 9:00am and before 12:00pm on tuesday, wednesday, thursday" in timezone America/Toronto.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.